| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.1.5.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.5 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_1_5_Team_Group_of_Providers_Registry_or_Directory |
| Title | AS.1.5 Team/Group of Providers Registry or Directory (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide access to a current directory, registry or repository of information on teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law. |
| Purpose | An organization may assign caregivers to teams that need to be registered as such. In another scenario, an organization might contract with a group of providers. The group would be listed by the group name or individually or both. A caregiver might be part of more than one team or group. All of these factors need to be supported. Information includes, but is not limited to: full name, address or physical location, and a 24x7 telecommunications address (e.g., a phone or pager access number). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide access to a current directory, registry or repository of information on teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.
An organization may assign caregivers to teams that need to be registered as such. In another scenario, an organization might contract with a group of providers. The group would be listed by the group name or individually or both. A caregiver might be part of more than one team or group. All of these factors need to be supported. Information includes, but is not limited to: full name, address or physical location, and a 24x7 telecommunications address (e.g., a phone or pager access number).
| AS.1.5#01 | dependent SHOULD |
The system SHOULD provide the ability to render a current directory, registry or repository of teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.1.5#02 | dependent SHOULD |
The system SHOULD provide the ability for authorized users to manage the assignment of providers to appropriate teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.1.5#03 | MAY |
The system MAY provide the ability to determine the identity of a provider's employer(s) for administrative or financial purposes through the use of internal, and/or external registry services or directories. |
| AS.1.5#04 | SHALL |
The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant) |
| AS.1.5#05 | SHOULD |
The system SHOULD provide the ability to manage care team membership. |
| AS.1.5#06 | dependent SHOULD |
The system SHOULD provide the ability to manage demographic and scheduling information on care team members, according to scope of practice, organizational policy, and/or jurisdictional law. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.1.5",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide access to a current directory, registry or repository of information on teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>An organization may assign caregivers to teams that need to be registered as such. In another scenario, an organization might contract with a group of providers. The group would be listed by the group name or individually or both. A caregiver might be part of more than one team or group. All of these factors need to be supported. Information includes, but is not limited to: full name, address or physical location, and a 24x7 telecommunications address (e.g., a phone or pager access number).</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a current directory, registry or repository of teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for authorized users to manage the assignment of providers to appropriate teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to determine the identity of a provider's employer(s) for administrative or financial purposes through the use of internal, and/or external registry services or directories.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant)</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage care team membership.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.5#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage demographic and scheduling information on care team members, according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.5",
"version" : "2.1.0",
"name" : "AS_1_5_Team_Group_of_Providers_Registry_or_Directory",
"title" : "AS.1.5 Team/Group of Providers Registry or Directory (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide access to a current directory, registry or repository of information on teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "An organization may assign caregivers to teams that need to be registered as such. In another scenario, an organization might contract with a group of providers. The group would be listed by the group name or individually or both. A caregiver might be part of more than one team or group. All of these factors need to be supported. Information includes, but is not limited to: full name, address or physical location, and a 24x7 telecommunications address (e.g., a phone or pager access number).",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.1.5-01",
"label" : "AS.1.5#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a current directory, registry or repository of teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.5#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.1.5-02",
"label" : "AS.1.5#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for authorized users to manage the assignment of providers to appropriate teams or groups of providers according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.5-03",
"label" : "AS.1.5#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to determine the identity of a provider's employer(s) for administrative or financial purposes through the use of internal, and/or external registry services or directories.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.5#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.5-04",
"label" : "AS.1.5#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant)",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.5#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.5-05",
"label" : "AS.1.5#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage care team membership."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.1.5-06",
"label" : "AS.1.5#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage demographic and scheduling information on care team members, according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.